Summary of open points:

• Tests now run for different timeseries uploads
• However, there seems to be some mismatches between the frontend and the backend processing
  • When uploading a timeseries file, the timeseries often gets displayed wrong in the plotly window. However, the processing then works correctly, since saving the asset form and then opening it again shows the timeseries graph correctly (I had this issue with the following file and tested both with an index column and without ninja_pv_52.1315_11.6401_corrected.csv)
  • When uploading a timeseries file, some checks are performed in the frontend and some in the backend. For instance, the timeseries length check happens in javascript and displays an error message, however it still allows the user to save the timeseries.

I think the better approach would be to conduct all checks in the backend and display them in the form upon validation. That way we ensure that all checks are in one place and there won't be any values saved that did not pass validation.